Problem Note 17633: Error when you attempt to rerun Import task after changing the SAS server
In SAS Enterprise Guide, if you replace your SAS Server after importing
a file, and then attempt to reimport your data on the new server, you
may receive the following error:
ERROR: Physical file does not exist
or
ERROR: No logical assign for filename #XXXXXX
This typically happens when you import a file on one server and run
Tools -> Replace SAS Server to change the processing SAS server for your
project. The import is still trying to import the original file from the
first server which does not exist on the second server.
You can workaround this problem using one of the following methods:
1) After you replace the SAS Server, save the project, close SAS
Enterprise Guide. Then reopen SAS Enterprise Guide, and rerun the
import task. This will sometimes use the correct server.
2) Another workaround is to recreate the Import Data task on the
second
server. After you run Replace SAS server, select File -> Import Data
to
reimport the exact same data from your second SAS server. In the new
Import task, specify the exact same output dataset as you have in the
original import. When you run this it will automatically generate an
arrow to your existing file in your process flow. After the import has
run successfully on the new server, you can remove the old Import Data
task and data from your Process Designer.
Please note: if you do not have any tasks that follow the output table
from your Import task, then when you remove the old Import Data task and
data, it will probably delete the newly created data also. If this
happens, rerun the Import task one more time and the data should be
recreated. If you have a task dependant on the output table, then when
you delete the old Import task and data, the remaining part of the flow
should automatically attach to your new flow.
Operating System and Release Information
SAS System | SAS Enterprise Guide | Microsoft Windows 2000 Advanced Server | 4.1 | 4.2 | 9.1 TS1M3 | 9.2 TS2M0 |
Microsoft Windows 2000 Datacenter Server | 4.1 | 4.2 | 9.1 TS1M3 | 9.2 TS2M0 |
Microsoft Windows 2000 Server | 4.1 | 4.2 | 9.1 TS1M3 | 9.2 TS2M0 |
Microsoft Windows XP Professional | 4.1 | 4.2 | 9.1 TS1M3 | 9.2 TS2M0 |
Microsoft Windows Server 2003 Standard Edition | 4.1 | 4.2 | 9.1 TS1M3 | 9.2 TS2M0 |
Microsoft Windows Server 2003 Enterprise Edition | 4.1 | 4.2 | 9.1 TS1M3 | 9.2 TS2M0 |
Microsoft Windows Server 2003 Datacenter Edition | 4.1 | 4.2 | 9.1 TS1M3 | 9.2 TS2M0 |
Microsoft Windows 2000 Professional | 4.1 | 4.2 | 9.1 TS1M3 | 9.2 TS2M0 |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.
Type: | Problem Note |
Priority: | medium |
Date Modified: | 2008-02-02 19:34:44 |
Date Created: | 2006-05-04 00:10:52 |